fix: countryCode property in Input type phone number#7684
fix: countryCode property in Input type phone number#7684vicky-primathon wants to merge 8 commits intoreleasefrom
Conversation
|
@somangshu I don't think this completely solve the issue here. When I try to bind the |
|
@riodeuno I can see that for the type phone number the @vicky-primathon I see that this does not function well in case of the currency as well. We need to fix the issue. |
somangshu
left a comment
There was a problem hiding this comment.
Change as mentioned above
@somangshu in case of currency, selected country code can be accessed as {{input.currencyCountryCode}} |
@vicky-primathon when I check:
Let me know if you have any doubts |
| label: `${item.name} (${item.dial_code})`, | ||
| value: item.code, | ||
| id: item.dial_code, | ||
| value: item.dial_code, |
There was a problem hiding this comment.
@vicky-primathon Will these changes effect existing users? How do we verify this in the UI?
There was a problem hiding this comment.
Will have to write migrations to update default selected code value from country code to dial_code
There was a problem hiding this comment.
@vivekverma2312 We will need to verify the migrations during QA. The approach would be open a bound input widget in this deploy preview, which was created in release.
|
Note for QA: We need a regression test for these types of input widgets. |
|
5f32380 to
51c2f21
Compare
|
/ok-to-test sha=51c2f21 |
|
/ok-to-test sha=51c2f21 |
|
/ok-to-test sha=51c2f21 |
| for (const key in child) { | ||
| if ( | ||
| typeof child[key] === "string" && | ||
| child[key].includes(".currencyCountryCode") |
There was a problem hiding this comment.
I can see that we're migrating bindings in the DSLs. However, I was wondering about the case where the bindings are in the actions? This seems like in those scenarios the applications might fail.
So, I was wondering if this was possible to be bound so far? From the looks of it, this feature wasn't functional so far, and we might be able to get away with only migrating DSLs.
@somangshu @vivekverma2312 @vicky-primathon
There was a problem hiding this comment.
That would be right, Since the feature has just been released we could expect minimum usage of this. However if a user complains what would be our response? Is there a way we can check migrations for the action as well? Since we just need to replace all occurrence, logically this is straightforward
There was a problem hiding this comment.
Migrating actions on the client will be tricky. We will need to implement a migration strategy for actions as well. Before we can get into this, we need to check with the backend to see if there are established mechanisms to deal with this. @sharat87
There was a problem hiding this comment.
Meanwhile, @vicky-primathon can you find out when this commit was merged into release?
There was a problem hiding this comment.
|
One comment. The rest looks good. |
51c2f21 to
75aad2b
Compare
|
/ok-to-test sha=75aad2b |
75aad2b to
bcb1c96
Compare
83cd5d1 to
c28b203
Compare
… code to currency migrations"
c28b203 to
cc7c48b
Compare
|
@vicky-primathon @riodeuno I disagree to CountryCode changing to DialCode, this is not the generic convention. Also since this is blocked by the backend migration, should we close this or draft it until unblocked |
|
@somangshu I don't have strong opinions on this. |
|
@riodeuno I said that because the name used in the first release used |
|
@vicky-primathon Lets close this PR since we're gonna introduce a v2 of input widget. We will do these changes on the v2. |


Description
Fix countryCode property in Input type phone number
Fixes #7475
Type of change
How Has This Been Tested?
Checklist:
Test coverage results 🧪
🟢 Total coverage has increased